refactor: remove InputStream-based parser methods and update parameter names#70
Open
fern-api[bot] wants to merge 1 commit intomainfrom
Open
refactor: remove InputStream-based parser methods and update parameter names#70fern-api[bot] wants to merge 1 commit intomainfrom
fern-api[bot] wants to merge 1 commit intomainfrom
Conversation
…r names This change removes several public methods that accepted InputStream parameters for lab report parsing, replacing them with File-based alternatives. Also updates internal parameter naming for better consistency and adds new optional fields to lab test requests. Key changes: - Remove parserCreateJob methods accepting InputStream, filename, and MediaType - Update lambda parameter names from (key, value) to (_key, _value) - Add labAccountId and labSlug fields to CreateLabTestRequest - Add labSlug field to LabTestsGetMarkersRequest - Add appointmentNotes field to RequestAppointmentRequest - Update lab parameter type in LabTestsGetPscAppointmentAvailabilityRequest 🌿 Generated with Fern
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
parserCreateJobmethods that acceptedInputStreamparameters have been removed. Use theFile-based versions ofparserCreateJobinstead. Several request classes now support additional optional fields for enhanced functionality.GetOrderTransactionResponse.getStatus()method now returnsOrderTransactionStatusenum instead ofString. Update your code to handle the enum type instead of string comparisons. TheParsingJob.getJobId()method has been removed - this field is no longer available in parsing job responses.LabAccountClientwithgetTeamLabAccounts()method for retrieving lab account information, and new request classesConvertCompendiumBodyandSearchCompendiumBodyfor compendium data operations.getTeamLabAccounts()method onRawLabAccountClientfor retrieving team lab account information with optional filtering. Additionally, lab test orders now support clinical notes through the newclinicalNotesparameter inCreateOrderRequestCompatible.additionalProperty()andadditionalProperties()methods on all request builders, allowing dynamic addition of custom key-value pairs to API requests. This enables extended flexibility when working with evolving API requirements.additionalProperty()andadditionalProperties()methods are now available on all request builder classes. These methods provide a fluent API for adding custom properties to requests while maintaining backward compatibility with existing code.additionalProperty()andadditionalProperties()builder methods are now available on all vitals request classes. These methods allow setting custom key-value pairs on API requests for passing additional parameters or metadata.additionalProperty()andadditionalProperties()methods available on all vitals request builders, allowing custom key-value pairs to be included in request objects.AppointmentBookingRequestnow supports optional appointment notes.additionalProperty()andadditionalProperties()are now available on all model classes to handle additional API response fields not explicitly defined in the schema. A newCanonicalCandidateclass has also been added.appointmentNotesfield onClientFacingAppointment. Builder patterns across multiple client-facing models have been enhanced with additional property support for greater flexibility.additionalProperty()andadditionalProperties()methods, enabling custom key-value pairs during object construction.additionalProperty()andadditionalProperties()are now available on all model classes, allowing you to set custom fields on objects for enhanced flexibility.additionalProperty()andadditionalProperties()are now available on all Vital API type builders for handling custom fields and extensible JSON objects.additionalProperty()andadditionalProperties()are now available on all client-facing type builders, allowing developers to set custom properties on objects that support additional fields beyond the defined schema.additionalProperty(String key, Object value)andadditionalProperties(Map<String, Object> additionalProperties)methods enable flexible construction of model objects with dynamic or unknown properties.additionalProperty()andadditionalProperties()methods are now available on all model builders, enabling dynamic property handling during object construction.additionalProperty()andadditionalProperties()methods are available on builders for client-facing model classes, allowing developers to set arbitrary key-value pairs when constructing objects.additionalProperty()andadditionalProperties()methods. This enables better handling of dynamic fields and improves forward compatibility.additionalProperty()andadditionalProperties()are now available on all grouped data model builders, enabling easier handling of additional fields returned by the Vital API.additionalProperty()andadditionalProperties()are now available on all grouped data type builders (GroupedIge, GroupedSteps, etc.), allowing dynamic addition of custom fields during object construction.additionalProperty()andadditionalProperties()are now available on all data model builders, allowing you to set custom properties on request and response objects. New enum valuesDERIVED_READINESSandSONORA_QUESThave been added for expanded functionality.additionalProperty()andadditionalProperties()are now available on model builders, providing better support for handling dynamic properties and future API extensions.ProviderIdConversionResponseandRelatedCandidatetypes are now available for provider ID mapping functionality. TheResultMetadatatype includes a new optionalgenderfield withResultMetadataGenderenum. Samsung Health is now supported as a provider option in theProvidersenum.